SSE = Server-Sent Events It is a one-way real-time communication method where the server continuously pushes data to the browser over a single long-lived HTTP connection. Think of SSE as: Server → Browser (only one-way) live updates Not two-way like WebSockets. How SSE works (simple explanation) Browser opens a connection: const es = new EventSource('/stream'); Server keeps the connection open and keeps sending events: data: Hello user data: New message arrived data: Notification updated Browser receives them instantly as they come. Where SSE is used? Live notificationsChat message updates (receive only)Live counters, analyticsStock tickersLive logsNews feed updatesDashboard updates SSE vs WebSocket Feature SSE WebSocket Direction One-way (Server → Client) Two-way Transport HTTP TCP Reconnection Built-in automatic Must implement Binary data No Yes Simpler Yes More complex Example Server sends: data: New notification for user 123 Browser receives: es.onmessage = (e) =andgt; console.log(e.data); Why choose SSE over WebSocket? SSE is better when: You only need server → browser updatesLightweight notificationsYou want automatic reconnectionYou want simpler code and less overheadAPI-driven architecture already uses HTTP

interview

home / developersection / interviews / what is sse?

Ask Question

What is SSE?

ICSM Computer 20 11-Dec-2025

.net technology

Updated on 11-Dec-2025

ICSM Computer

IT-Hardware & Networking

Ravi Vishwakarma is a dedicated Software Developer with a passion for crafting efficient and innovative solutions. With a keen eye for detail and years of experience, he excels in developing robust software systems that meet client needs. His expertise spans across multiple programming languages and technologies, making him a valuable asset in any software development project.

Can you answer this question?

Answer

1 Answers

ICSM Computer

11-Dec-2025

SSE = Server-Sent Events

It is a one-way real-time communication method where the server continuously pushes data to the browser over a single long-lived HTTP connection.

Think of SSE as:

Server → Browser (only one-way) live updates

Not two-way like WebSockets.

How SSE works (simple explanation)

Browser opens a connection:

const es = new EventSource('/stream');

Server keeps the connection open and keeps sending events:

data: Hello user
data: New message arrived
data: Notification updated

Browser receives them instantly as they come.

Where SSE is used?

Live notifications
Chat message updates (receive only)
Live counters, analytics
Stock tickers
Live logs
News feed updates
Dashboard updates

SSE vs WebSocket

Feature	SSE	WebSocket
Direction	One-way (Server → Client)	Two-way
Transport	HTTP	TCP
Reconnection	Built-in automatic	Must implement
Binary data	No	Yes
Simpler	Yes	More complex

Example

Server sends:

data: New notification for user 123

Browser receives:

es.onmessage = (e) => console.log(e.data);

Why choose SSE over WebSocket?

SSE is better when:

You only need server → browser updates
Lightweight notifications
You want automatic reconnection
You want simpler code and less overhead
API-driven architecture already uses HTTP

interview

What is SSE?

ICSM Computer

Can you answer this question?

1 Answers

SSE = Server-Sent Events

Server → Browser (only one-way) live updates

How SSE works (simple explanation)

Where SSE is used?

SSE vs WebSocket

Example

Server sends:

Browser receives:

Why choose SSE over WebSocket?

Liked By